For anyone following a similar path, my attempt to serve SMB over NFS: NFSv4.1: racing open/unlink/recreate of the same filename can leave processes unkillable.

The challenge here is that FSKit is at a point where it is genuinely useful, even in a network context. Indeed, and I can see that based on your example. Thanks again for engaging here and for providing very useful responses.

Thanks for the response, Kevin! I appreciate you taking the time to address these issues, even though I might be disappointed that FSKit isn't yet up to the task. The current FSKit documentation points to things like "a network resource you identify with a URL" or "some sort of network address for a remote file system" or "to network connections, and beyond." Maybe an update to the documentation would steer would-be adopters appropriately. For me, it sounds like I'll just have to be patient.

Just adding a comment that fisheye projection could be along the lines of what Google has described in their spatial media specs: https://github.com/google/spatial-media/blob/master/docs/vr180.md

I haven't seen any specific recommendations from Apple, but for comparison, the "Highlining" video appears to be delivering 4320x4320, HRD10, 90fps content in fisheye projection at ~50Mbps for its best presentation.

By the way, it looks like there's a small bug in the side-by-side example code. In Coverter.swift around line 130, the else block that marks frameInput as finished should be in response to a nil sampleBuffer. Otherwise, the conversion will never end. To fix it, just move that else block to be a condition of the "if let sampleBuffer" logic (essentially un-indenting the logic one level...while fixing-up the parenthesis, of course).

Also, I ran across this post about creating a simple immersive 360º media player: https://medium.com/@pat.schnitzerb/how-to-make-a-360-videoplayer-for-visionpro-74e42e239e5 Note that the same technique can be used to project 180º media if you provide hemispherical geometry.

I'm not sure that I follow your question exactly, but there's no indication that I've seen that the framework natively supports playing back over/under-style content. You probably want to encode each eye to its own layer in a MV-HEVC file. Then, as far as I know, you need to build a player that takes the stereo MV-HEVC content and projects it onto a sphere/hemisphere in a RealityKit scene to see it in 3D.

As far as I know, there is no built-in method to playback half equirectangular (180º) or full equirectangular (360º) content. Many have looked (including me). Perhaps this is an upcoming feature of AVPlayer. In the meantime, it looks like you have to do what all other immersive players have done: create a RealityKit scene, add a hemisphere (180º) or full sphere (360º), and setup the AVPlayer to project to that surface. I don't know if this is the final/recommended way to do it, but it works well.